Release notes 2019-2021

2021r3.000

Fix for POST /fulldaYs calls of linear schedule BAPI

In previous versions, a crash occurred when creating all transmissions for one day via the POST /fullDays call of the linear schedule BAPI. This happened when the transmissionID was not present in the call, because it did not get automatically generated.

This issue has been fixed.

2021r2.001

API version: v1.2.1

New attributes

Some new attributes have been added to the response for the GET /transmissions/:transmissionId and GET /transmissions to search for transmissions:

  • contractId: the external reference of the linked contract
  • contractNumber: the number of the linked contract
  • runNumber: the run number of the right used by the transmission
  • runType: the run type of that the transmission uses - free rerun or run
  • nrOfProgramSegments: the total number of program segments in the transmission across the different transmission blocks

An example of the GET call:

{
    "title": null,
    "transmissionId": "5655715812",
    "channel": "MgX",
    "template": "Tx",
    "startDate": "2021-07-27",
    "startTime": "16:00",
    "duration": "01:00:00",
    "announcedTime": "16:00",
    "contentId": "3611445527",
    "productCode": "Kine4",
    "live": false,
    "contractId": "2353219000",
    "contractNumber": "21042020",
    "runNumber": 1,
    "runType": "run",
    "nrOfProgramSegments": 2
}

Fix for empty channel or template

Previously, if you used a POST or PUT /transmission call and left the channel or template attributes empty (by specifying "template": ""), a response with status code 500 would be returned and the BAPI service (WOnRESTDefinitionService) would crash because it could not handle this request.

Now this issue has been fixed and the following response is returned when either the channel or template is empty:

{
    "statusCode": "422",
    "message": "Operation cannot be completed due to violations",
    "timestamp": "2021-10-04T12:02:15Z",
    "concept": "Transmission",
    "id": "11002266",
    "errors": [
        {
            "errorCode": "LINEARSCHEDULE-00010",
            "description": "Please provide a template and channel when creating linear transmission",
            "data": []
        }
    ]
}

2021r1.001

Linear schedule API and press target lookup tables

In a previous version, EPG fields were added to the linear schedule API to be able to import competitor schedules.

To be able to create publication records with those calls, the press target is a mandatory field and important for some restrictions on the length of fields.

The logic to find the press target was: "The press target of the publication record is the press target of the channel. If there is no press target on the channel, the default press target is taken."

With the new behaviour (RN-4225), only the publication system is defined on the channel. There is no more press target on the publication system. The logic of finding the press target is determined by a lookup table.

Therefore, the logic to find the press target for the Linear schedule API was also adapted:

  • The press target should be found in the lookup table for linear press targets for the combination of the channel indicated in the call, and the publication system defined on that channel in WHATS'ON.

  • Since the press type divides the fields into different sections, the lookup rule for that channel and publication system with an empty press type is taken to cover all possible fields in the call.

  • Additionally, if there is no lookup table or there is no result from the lookup table for this combination of channel and system, the default press target on the WOnPressTarget drop-down list should be taken.

2021r1.000

EPG metadata in linear schedule API

It is possible to create and update transmissions via a REST call. It is also possible to link products to these transmissions and to create a full day of transmissions in one call.

From this version, both the calls to create and update a transmission, and the call to post a full day of transmissions, will be expanded with information that is stored on the program guide record of that transmission.

Three new fields have been created for the EPG part of the linear schedule call:

  • videoFormat

  • IsRepeat

  • runningYear

2020r1.002.000

POST full day of transmission in linear schedule API

A new call is created to post a full day of transmissions using the linear schedule API.

External reference cannot be cleared by BAPI

Within any POST and PUT call, if a an attribute is sent empty, WHATS'ON will clear that field. Previously, this was also possible with the external reference of a transmission.

Now, this is fixed. When no external reference is provided but the attribute is sent empty or null, we will ignore that tag and proceed as if there was no ID field (external reference) provided. This means that it should remain as is in a PUT call or return a new one in a POST call.

2019r1.000.000

API version: v1.0.0

Addition of Linear schedule API

From this version on, it is possible to manage linear transmissions using the Linear schedule API.